Contents of the LinkBuilder Diskette The diskette shipped with the LinkBuilder FDDI Workgroup Hub contains the following: . PARTNO file ù LinkBuilder FDDI system software image, version 1.1a SNMP . LinkBuilder FDDI MIB files LBFDDI.MIB - LinkBuilder FDDI concise MIB definition. LBFDDI.OID - LinkBuilder FDDI Object IDs for SunNet Manager. LBFDDI.TRP - LinkBuilder FDDI Trap definitions for SunNet Manager. LBFDDI.SCH - LinkBuilder FDDI Schema for SunNet Manager. IVLBFDDI.MIB - LinkBuiler FDDI MIB definition for 3Com ISOVIEW. ù This README.TXT file Downloading the new images to the FDDI Workgroup Hub can be disruptive to the ring. The download sequence will isolate the hub from the ring during the power-on self-test (POST) and may cause the ring to wrap or isolate attached stations. Downloads impact the ring the least when the hub is attached to the ring in a ring of trees configuration as a single attachment hub. 3Com recommends that software upgrades be carefully planned to minimize network downtime. Corrections in the User Guide The corrections and clarifications provided below pertain to the LinkBuilder(R) FDDI Workgroup Hub User Guide. Page 2-14: Check the Baud Rate Setting After Post When the power-on self-test (POST) is run, the hub's serial port output defaults to 9600 baud regardless of the baud rate setting in nonvolatile RAM. If you have set the console baud rate to other than 9600, you may need to adjust the attached terminal baud rate after POST has finished. The default baud rate setting is 9600. Page 2-14: Removing Modules The first two steps for removing modules as given in the User Guide should be reversed. They should read: 1. Enter the disconnect command. This disables all ports and isolates the hub from the ring. 2. Disconnect all cables connected to the module that you want to remove. If possible, you should always turn off the power before attempting to remove or insert hardware. Removing modules from the hub with the power on will not damage the hardware. However, the software may not be able to distinguish between intentional removal and catastrophic failure of a media module. As a result, some errors will be entered in the fault log and in some cases may fill the fault log entirely. The most common error resulting from the removal of a media module is 05000002 (bus error). Other errors may also occur. Check the fault log for valid errors before you remove any module. Also, clear the fault log (using the clear log command) after all changes are complete and the system has been reinitialized. Pages 3-9, 3-10, and 3-11: Accessing the Primitive Console Command Mode The procedure for accessing the primitive console command mode has been modified. To access the primitive console command mode: 1. Press the RESET button once, or enter the reset command. During the subsequent power-on self-test (POST), the status LED flashes amber/green for 10 seconds, indicating that the primitive console command mode is being accessed. 2. Press the RESET button again. POST is reinitialized. When POST is completed, this prompt appears for 10 seconds: Press Ctrl-P to enter Primitive console All other keys except [Ctrl] and [P] are ignored during this 10-second interval. 3. Press [Ctrl] + [P]. The hub is now in the primitive console command mode. If you do not access the primitive console command mode, POST executes the system software resident in flash memory. Prior to execution of the system software, POST verifies that flash memory is not corrupted. This process takes about 20-30 seconds. During this time the status LED is off. After flash memory has been verified, the status LED turns green when the system is fully initialized. Within a short time, the modem initialization string AT&F is briefly displayed. When the AT&F display disappears, you can access the management console command mode by pressing [Enter]. When there is no active console session or if a console session times out, AT&F will be displayed periodically to determine if a modem is present. You must wait for the AT&F to disappear before pressing [Enter] to enter the management console command mode. Page 5-20: route dump and route add Commands Changes have been made in the route command display and description. When you enter the route dump command, a metric value appears in the subsequent display, as explained below: ù A metric of 0 indicates that the entry is a host. ù A metric of 1 indicates that the entry is a gateway. You can include a metric of 0 or 1 with the route add command. If you enter a value greater than 1, it is converted to 1. If the metric is not entered, 1 is assumed, which designates the entry as a gateway. The default gateway, whether entered using the route add command or the set gateway command, sets the metric to 1 regardless of the metric option given. The metric option does not indicate the number of hops to the destination network, as stated on page 5-20. It does indicate whether the entry is a host or a gateway. Page 5-21: Fault Log Display A reset count has been added to the fault log display header. When you enter the show log command, the fault log header appears, as shown in the example below: Fault Log: [# 10] The number corresponds to the number of times the hub has been reset and allows you to correlate fault log entries with a given reset shown in the fourth column of the display. Page A-7: Management Module Failure Error Code This is a clarification of the management module failure error code. The management module failure error code is 0xxxxxxx. If the second digit is 0 or 1 (that is, of the form 00xxxxxx or 01xxxxxx), the error code indicates a nonvolatile RAM error or a flash memory error on the management module, not a failure of the management module itself. Page C-22: show rev Command This explains the length of time the show rev command takes to complete. When you enter the show rev command in primitive console command mode, the display verifies that flash memory is not corrupted before reporting the firmware and software version strings. This process takes about 20-30 seconds. Pages 2-26 and 2-27: Installing an Optical Bypass Switch The example given in the user guide assumes that the optical bypass switch ports labeled A and B are logical extensions of the hub's A and B ports. The orientation of the bypass switch A and B MIC connectors and port receptacles may vary. Please refer to the installation instructions for your specific brand of optical bypass switch to insure that it is properly connected to the hub and dual trunk ring. New Console command This version adds a repeat command (!!) not documented in the current user guide. Typing !! will echo the previously entered command and allow you to edit it, if necessary, using the backspace key. The command can be re-issued by depressing the enter key. LinkBuilder FDDI WorkGroup Hub MIB limitations: 1. The following MIB-II counters always return 0. ipInUnknownProtos ipInDiscards ipOutDiscards ipFragOKs ipFragFails ipFragCreates ipRoutingDiscards 2. The following MIB objects are read-only. AtEntry ::= SEQUENCE { atIfIndex INTEGER, atPhysAddress PhysAddress, atNetAddress NetworkAddress } Note: this MIB object is deprecated. Use IpNetToMediaEntry. ipDefaultTTL ipForwarding IpRouteEntry tcpConnState fddimibMACRequestedPaths fddimibMACNotCopiedThreshold fddimibPORTRequestedPaths 3. Set operations on the following MIB objects are limited. IpNetToMediaEntry - A SET requires each member in the entry to be set. Sets to individual members are not allowed. fddimibSMTStationAction OBJECT-TYPE SYNTAX INTEGER { other(1), -- none of the following connect(2), disconnect(3), path-Test(4), self-Test(5) disable-a(6), -- set not allowed disable-b(7), -- set not allowed disable-m(8) -- set not allowed } fddiPATHTVXLowerBound - Minimum value allowed is 80 nanoseconds. 4. The MIB-II egp group is not supported. 5. In the fddimibMACCountersEntry, the following two MIB items have been added to satisfy specific SNMP manager MIB compiler needs. pseudoMACSMTIndex INTEGER, pseudoMACIndex INTEGER